Skip to content

Update version to 2.2.6 across project files#505

Merged
MervinPraison merged 1 commit intomainfrom
develop
May 24, 2025
Merged

Update version to 2.2.6 across project files#505
MervinPraison merged 1 commit intomainfrom
develop

Conversation

@MervinPraison
Copy link
Copy Markdown
Owner

  • Incremented PraisonAI version from 2.2.5 to 2.2.6 in pyproject.toml, uv.lock, and all relevant Dockerfiles for consistency.
  • Updated test command patterns in GitHub Actions workflows for improved clarity and functionality.
  • Ensured minimal changes to existing code while maintaining versioning accuracy.

- Incremented PraisonAI version from 2.2.5 to 2.2.6 in `pyproject.toml`, `uv.lock`, and all relevant Dockerfiles for consistency.
- Updated test command patterns in GitHub Actions workflows for improved clarity and functionality.
- Ensured minimal changes to existing code while maintaining versioning accuracy.
@MervinPraison MervinPraison merged commit 9e9f178 into main May 24, 2025
7 of 10 checks passed
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented May 24, 2025

Warning

Rate limit exceeded

@MervinPraison has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 0 minutes and 11 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between c5dd6af and 13c6eec.

⛔ Files ignored due to path filters (1)
  • uv.lock is excluded by !**/*.lock
📒 Files selected for processing (13)
  • .github/workflows/test-comprehensive.yml (2 hunks)
  • .github/workflows/unittest.yml (1 hunks)
  • docker/Dockerfile (1 hunks)
  • docker/Dockerfile.chat (1 hunks)
  • docker/Dockerfile.dev (1 hunks)
  • docker/Dockerfile.ui (1 hunks)
  • docs/api/praisonai/deploy.html (1 hunks)
  • docs/developers/local-development.mdx (1 hunks)
  • docs/ui/chat.mdx (1 hunks)
  • docs/ui/code.mdx (1 hunks)
  • praisonai/cli.py (1 hunks)
  • praisonai/deploy.py (1 hunks)
  • pyproject.toml (2 hunks)
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@netlify
Copy link
Copy Markdown

netlify bot commented May 24, 2025

Deploy Preview for praisonai ready!

Name Link
🔨 Latest commit 13c6eec
🔍 Latest deploy log https://app.netlify.com/projects/praisonai/deploys/6831f65c86c72800086d5a80
😎 Deploy Preview https://deploy-preview-505--praisonai.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @MervinPraison, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

Hello team, Gemini here with a summary of this pull request. The primary goal of this PR, authored by MervinPraison, is to update the project's version from 2.2.5 to 2.2.6 across various configuration and documentation files. This ensures consistency in the specified PraisonAI version used throughout the project, including Docker builds, dependency locks, and documentation examples. Additionally, a minor adjustment was made in the CLI logic regarding the default agent file.

Highlights

  • Version Update: The PraisonAI version has been consistently updated from 2.2.5 to 2.2.6 in the main project configuration (pyproject.toml), the dependency lock file (uv.lock), several Dockerfile configurations, and various documentation snippets that include Dockerfile examples or installation instructions.
  • CLI Logic Adjustment: A small change in praisonai/cli.py removes the explicit default assignment of self.agent_file to "agents.yaml" when no command is provided, allowing the value set during the class constructor to be preserved instead.

Changelog

Click here to see the changelog
  • docker/Dockerfile
    • Updated the praisonai package version from 2.2.5 to 2.2.6 in the RUN pip install command (line 4).
  • docker/Dockerfile.chat
    • Updated the praisonai package version from 2.2.5 to 2.2.6 in the RUN pip install command (line 16).
  • docker/Dockerfile.dev
    • Updated the praisonai package version from 2.2.5 to 2.2.6 in the RUN pip install command (line 18).
  • docker/Dockerfile.ui
    • Updated the praisonai package version from 2.2.5 to 2.2.6 in the RUN pip install command (line 16).
  • docs/api/praisonai/deploy.html
    • Updated the praisonai package version from 2.2.5 to 2.2.6 in the embedded Dockerfile example code (line 113).
  • docs/developers/local-development.mdx
    • Updated the praisonai package version from 2.2.5 to 2.2.6 in the embedded Dockerfile example code (line 30).
  • docs/ui/chat.mdx
    • Updated the praisonai package version from 2.2.5 to 2.2.6 in the embedded Dockerfile example code (line 158).
  • docs/ui/code.mdx
    • Updated the praisonai package version from 2.2.5 to 2.2.6 in the embedded Dockerfile example code (line 211).
  • praisonai/cli.py
    • Removed the else block that defaulted self.agent_file to "agents.yaml" if no command was provided (lines 159-161 removed).
  • praisonai/deploy.py
    • Updated the praisonai package version from 2.2.5 to 2.2.6 in the generated Dockerfile content string (line 59).
  • pyproject.toml
    • Updated the project version from 2.2.5 to 2.2.6 in the [project] section (line 3).
    • Updated the project version from 2.2.5 to 2.2.6 in the [tool.poetry] section (line 92).
  • uv.lock
    • Updated the locked version for the praisonai package from 2.2.5 to 2.2.6 (line 3617).
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


Version bumps abound,
From two point two point five it leaps,
To two point two six.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request primarily focuses on updating the PraisonAI version to 2.2.6 across various project files, which has been done consistently.

However, there are a couple of points that need attention:

  1. A functional change has been introduced in praisonai/cli.py that modifies how the agent_file is handled. This change, while potentially an improvement, is not directly related to versioning and could have implications for existing users. It's important to clarify its intent and ensure it's appropriately communicated.
  2. The PR description mentions updates to GitHub Actions workflows, but no such files are included in the diff. This discrepancy should be addressed by updating the PR description to accurately reflect the changes made.

Given these points, especially the functional change in cli.py and the PR description mismatch, I recommend addressing these before merging. I am unable to approve pull requests, so please ensure these points are discussed and resolved, and that other reviewers approve the changes.

Summary of Findings

  • Version Update Consistency: The version was successfully and consistently updated to 2.2.6 across pyproject.toml, uv.lock, all Dockerfiles, and relevant code snippets in documentation files. This aspect of the PR is well-executed.
  • Functional Change in praisonai/cli.py: A functional change was made in praisonai/cli.py (lines 159-161 on the 'before' side) that alters how agent_file is handled. This change preserves the agent_file set during class instantiation if no command-line arguments override it. This is a behavioral modification that should be explicitly documented in the PR description, and its inclusion in a version-bump PR should be clarified. (Commented with 'medium' severity)
  • PR Description Discrepancy: The PR description states: "- Updated test command patterns in GitHub Actions workflows for improved clarity and functionality." However, no GitHub Actions workflow files were modified in this pull request. The PR description should be updated to accurately reflect the changes included. (Addressed in general feedback with 'medium' severity)

Merge Readiness

This pull request primarily handles the version bump to 2.2.6, which is done correctly. However, there's a functional change in praisonai/cli.py whose scope and communication need clarification. Additionally, the PR description mentions GitHub Actions workflow updates that are not present in the diff.

I recommend that these points, particularly the cli.py change and the PR description accuracy, be addressed before merging. As I am an AI assistant, I am not authorized to approve pull requests. Please ensure further review and approval from other maintainers after these points are resolved.

shaneholloman pushed a commit to shaneholloman/praisonai that referenced this pull request Feb 4, 2026
Update version to 2.2.6 across project files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant